PC Direct 1995 May

home *** CD-ROM | disk | FTP | other *** search

/ PC Direct 1995 May / PC Direct CD-ROM (May 1995).ISO / ipe / manuals / sm43 / smref.txt < prev next >

Wrap

Text File | 1994-07-31 | 49.1 KB | 1,173 lines

The following chart describes where you can find each of the appendices provided with SiteMeter: APPENDIX CONTENTS FILE NAME A Advanced Utilities SMref.txt B Troubleshooting SMref.txt C Using Brequest Btrieve.txt D Btrieve Status Codes Btrieve.txt E NMS Smart-Launch Support NMS.txt F Introduction to Crystal Reports Crystal.txt G Using Crystal Reports Crystal.txt H Practical Crystal Reports Crystal.txt SMREF.TXT Headings: 1.0 Appendix A Advanced Utilities 1.1 About SiteMeter's Utilities 1.1.1 Utilities List 1.2 Swatcher TSR Method 1.2.1 Loading Swatcher 1.2.2 Note About Swatcher 1.2.3 Running DSW 1.2.4 What DSW Does 1.2.5 Potential DSW Problems 1.3 SYSMOD 1.3.1 What is SYSMOD? 1.3.2 Using SYSMOD 1.3.3 Functionality 1.3.4 ADDDEVICE [DeviceToAdd][Key][Option] 1.3.5 ADDLINE [LineToAdd][Key][Option] 1.3.6 ADDPATH [PathKey][DirectoryKey][Option] 1.3.7 CFGSETSTRONG [Key][NewValue] 1.3.8 REPLACEKEY [Key][DelKey][NewItem] 1.3.9 REPLACELINE [Key][NewLine] 1.3.10 WRITEINISTR [SectionName][KeyName][NewValue] 1.3.11 Halting SYSMOD Updates 1.4 SLOCK/SUNLOCK 1.4.1 Using SLOCK & SUNLOCK 1.4.2 Command Line Reference 1.4.3 Error Levels 1.4.4 SLOCK Errorlevels 1.4.5 SUNLOCK Errorlevels 2.0 Appendix B Troubleshooting 2.1 Error Messages 2.2 Troubleshooting 2.2.1 Installation and Set Up 2.2.2 Cannot Meter 2.2.3 LockSet Does Not Release 2.2.4 SMRUP Patches 2.2.5 SMRNLM.EXE 73,092 6-02-94 2.2.6 SMRUP3.EXE 05-25-94 1,788,902 11:48a 2.2.7 SiteMeter Reports (Sreport.exe) 2.2.8 BTRIEVE 2.2.9 Changing the SiteMeter Messages 1.0 Appendix A Advanced Utilities Chapter 8 described the monitoring features available for network users. This appendix explains how to use SiteMeter's advanced utilities. 1.1 About SiteMeter's Utilities The utilities described in this chapter are provided for you if you have decided not to use the SiteMeter Proxy NLM as the metering and file protection method for your LAN. 1.1.1 Utilities List The following lists the utilities described in this chapter: o SWATCHER o DSW o SYSMOD o SUNLOCK o SLOCK Each of these utilities is fully explained in the following sections. 1.2 Swatcher TSR Method If you have chosen to use the Swatcher TSR method of metering and file protecting your LAN, you may need to become familiar with the following metering utilities: o Swatcher o DSW Swatcher is a TSR and must be loaded in order to properly meter and protect the files on your LAN. 1.2.1 Loading Swatcher Swatcher must be loaded from the DOS prompt. To load Swatcher type: Swatcher <ENTER> Swatcher must be loaded AFTER loading IPX and NETX shells. It should not be loaded high; it should be in conventional memory. We recommend loading Swatcher from the AUTOEXEC.BAT before logging in to the network. NOTE: DO NOT LOAD Swatcher.com via the NetWare login scripts (either personal or system), as inconsistent and/or inappropriate metering behavior may result. If you try to load Swatcher after login and the Security Scan Interval is set and you have a lengthy login script, you may be disconnected before you get a chance to load Swatcher. 1.2.2 Note About Swatcher Since membership in a group determines local drive access, SiteMeter must know who you are when you load Swatcher. This can only be accomplished if Swatcher is loaded AFTER you log in. For security reasons, however, you may prefer that Swatcher is loaded BEFORE login time. To address this, we have created DSW.COM. Users can load Swatcher before logging in, but at this time SiteMeter cannot identify the users and therefore will not restrict access to local drives. ONCE a user is logged in, you must run DSW.COM; it reads the CURRENT server's information about how it should handle the user's local drives and then changes Swatcher accordingly. DSW is only able to update Swatcher ONE TIME--the FIRST time it is run. Further attempts to run DSW do not change Swatcher, although you receive a message on the screen indicating that it has updated Swatcher. 1.2.3 Running DSW DSW is run through the system Login Script. Here is a sample login script: MAP F:=FS/SYS:LOGIN DRIVE F: #DSW 1.2.4 What DSW Does DSW reads the information the server holds about a user, including whether to disable his or her local drives completely, disable only his or her local .EXE and .COM files, or give the him or her FULL rights. This information is sent to Swatcher. Swatcher receives it and updates its values accordingly. 1.2.5 Potential DSW Problems If more than one person uses the same PC and these people have different local drive rights, a problem could arise. SCENARIO 1: Person A (in local drives disabled group) loads Swatcher, logs in, and Swatcher is updated. Person B (who has full rights) logs in to the same PC that Person A was using. Because Swatcher is NOT updated again, Person B does not get access to the drives. Person B must reboot and reload Swatcher to get the appropriate rights. SCENARIO 2: Person A (with Full Rights) logs out. Person B (with no rights) logs into the same PC and now has full rights to the local drives. To prevent this problem, the PC should be re-booted between users. 1.3 SYSMOD 1.3.1 What is SYSMOD? SYSMOD is a McAfee utility designed to help network administrators edit files. With SYSMOD, you can edit users' files without going from workstation to workstation to do so. This utility is installed in the directories SITEMETR or BWORKS and PUBLIC. You can use SYSMOD if you prefer to edit your users' files manually. 1.3.2 Using SYSMOD Use the following procedure to implement the SYSMOD program: Make sure that the path to the .INI files is included as either a search drive in the case of users' Windows residing on the network or in the users' path statements located in their AUTOEXEC.BAT files for local Windows on the C: drive. Example lines for login script: Map ins s16:=SYS:\USER\%LOGIN_NAME\WINDOWS INCLUDE SYS:PUBLIC\SMRUSER.BAT Example line for the SMRUSER.BAT using the INCLUDE command: SYSMOD WIN.INI REPLACEKEY LOAD SWATCHER.COM SWATCHER.COM 1.3.3 Functionality This section documents the SYSMOD program and its functionality. All SYSMOD functions follow a basic format: SYSMOD <filename.ext>functionName parameter1...parameterN Below is a list of functions and their associated parameters. An example is also provided for each function. Note that when a parameter can be Null, it must still be entered, but use the NULL keyword. For example, SYSMOD CONFIG.SYS ADDDEVICE C:\HIMEM.SYS NULL BEFORE This would place the device= line at the beginning of the file. (See ADDDEVICE for details.) The filename specified must exist; SYSMOD, however, will intelligently determine the location of the file for you. If you specify AUTOEXEC.BAT or CONFIG.SYS (with no path), SYSMOD will automatically look on your boot drive for the file. If you specify a filename with no path (e.g., SYSTEM.INI), SYSMOD will look in your path for the file. If you specify a full path to the file, SYSMOD will look in the explicit path for the file. If the file cannot be found, SYSMOD aborts with an error. 1.3.4 ADDDEVICE [DeviceToAdd][Key][Option] This function adds a new DEVICE= line to a system file (typically the DOS CONFIG.SYS). Specify the path and driver name in the DeviceToAdd (e.g., C:\WINDOWS\EMM386.EXE). Specify a key value to search for in Key (e.g., HIMEM.SYS), and where to place DeviceToAdd BEFORE or AFTER Key in Option. For example: SYSMOD CONFIG.SYS ADDDEVICE C:\WINDOWS\EMM386.EXE HIMEMSYS AFTER would place a "device=c:\windows\emm386.exe" after the "device=himem.sys" line in the CONFIG.SYS. If Key is NULL or the key specified is not found, the device line is added at the beginning or end of the file. 1.3.5 ADDLINE [LineToAdd][Key][Option] This function adds a line of text to a system file. Specify the entire line of text you wish to add in LineToAdd. Specify a reference key value in Key that you would like to position LineToAdd in reference to. Option (BEFORE or AFTER) specifies whether LineToAdd is placed BEFORE or AFTER Key. Again, if Key is NULL, then LineToAdd is placed at the beginning or the end of the file. For example, SYSMOD AUTOEXEC.BAT ADDLINE C:\DOS\SMARTDRV NETX AFTER would place a new line (c:\dos\smartdrv) after the line specifying netx (if found, otherwise it would go at the end of the file). 1.3.6 ADDPATH [PathKey][DirectoryKey][Option] This function adds a sub directory to a path environment variable. Specify the name of the path environment variable to edit (PATH for DOS, or DPATH for OS/2) in PathKey and the subdirectory to add in PathToAdd. DirectoryKey specifies the sub directory that PathToAdd will be placed BEFORE or AFTER. Option is either BEFORE or AFTER. If DirectoryKey is a null string, ADDPATH will place PathToAdd at the beginning or end (respectively) of the path statement. If the key specified in PathKey is not found, then a new one is added, with a "SET" prepended. This allows for adding path like environment variables such as "SET TEMP=," and so on. NOTE: This function can also be sued to edit other lines, such as a TEMP environment variable, or any other line that does something like "SET envvar>=d:\path." For example, SYSMOD AUTOEXEC.BAT PATH C:\WINDOWS C:\DOS BEFORE would place c:\windows in the path statement before c:\dos. If c:\dos isn't in the path, then c:\windows would be placed at the beginning of the path statement. 1.3.7 CFGSETSTRONG [Key][NewValue] This function sets a strong variable in a system file (e.g., STACKS 9,256, DOS=HIGH etc.). Specify the variable in Key and a string value to set in NewValue. For example, SYSMOD CONFIG.SYS CFGSETSTRING STACKS 9,256 would set the value of the STACKS statement to 9,256. 1.3.8 REPLACEKEY [Key][DelKey][NewItem] This function works like REPLACELINE, except that it replaces a key value rather than the entire line. Use Key to locate the line, DelKey is the key value to replace, and NewItem is the new value. The new value can be NULL, in which case DelKey will be removed. For instance: SYSMOD WIN.INI REPLACEKEY LOAD SWINAPP.EXE SWATCHER.COM would replace the swinapp.exe reference in the load=line of the WIN.INI with swatcher.com. 1.3.9 REPLACELINE [Key][NewLine] This function replaces an existing line in a system file with a new line. Specify the key value of the line you wish to replace, such as PATH or COMSPEC (or DEVICE, for that matter) in Key. Specify the new value of the entire line in NewLine. If Parameter 2 is a null string, then the line will be deleted. For instance: SYSMOD AUTOEXEC.BAT REPLACELINE COMSPEC NULL would delete the existing COMSPEC line. 1.3.10 WRITEINISTR [SectionName][KeyName][NewValue] This function mimics the Windows API function WritePrivateProfileStrong0. It expects the file you're modifying to be in the Windows INI file format. This function writes NewValue to the INI file under SectionName in KeyName. However, if SectionName doesn't exist, then a whole new section is added to the end of the INI file, with a new key=value added in that section. If the section was found, but the KeyName wasn't found, the new key value is added directly after SectionName. For instance: SYSMOD SYSTEM.INI BOOT KEYBOARD.DRV BDIKBD.DRV would change the existing keyboard.drv= entry in the [boot] section of the system.ini to read keyboard.drv-bdikbd.drv. 1.3.11 Halting SYSMOD Updates This section describes how to stop SYSMOD from updating a user's files every time he or she logs in. To instruct SYSMOD to update a user's .ini file only once, add similar lines to the system login script: MAP F:=SYS:USER\%LOGIN_NAME #COMMAND /C SITE.BAT MAP DEL F: where site.bat is a .bat file with the following lines: if exist f:sitedone.doc goto end call smruser.bat copy sitedone.doc f: :end where sitedone.doc is a dummy text file that = 'sysmod has already run.' This code creates a flag that indicates if sysmod has already run. SYSMOD will see this and not run. 1.4 SLOCK/SUNLOCK This section explains how to use SiteMeter's SLOCK/SUNLOCK utilities for metering from a batch file. In this section, "LockSet" is a McAfee term for a metered application. NOTE: You must have Read, Write, Open, Create, Delete and Search rights in the directory where the SITEDATA file is stored if you wish to use SLOCK and SUNLOCK. The default home directory is SYS:SYSTEM\SITEMETR. SLOCK and SUNLOCK allow a user to secure or lock a position in the desired application and then free or unlock that position for another user. These commands should be included in batch files or other means such as a menu system setup. The following batch file consists of the appropriate SiteMeter commands to lock and unlock positions into the LockSet SYSCON. The batch file looks like this: SLOCK SYSCON* (where SYSCON is metered APP.Name) If errorlevel = 100 SYSCON SUNLOCK SYSCON * (where SYSCON is metered App. Name) NOTE: The errorlevel = 100 tests the return code from SLOCK. All return codes for SLOCK and SUNLOCK are listed later in this appendix. The asterisk (*) will display SLOCK messages. SYSCON is the metered application name as it appears in the metering definition. By requiring people to use a batch file to run SYSCON, you are modifying the way users operate that application, resulting in increased control over the network through SiteMeter, even without SWATCHER loaded. 1.4.1 Using SLOCK & SUNLOCK This section describes how to use SLOCK and SUNLOCK. Use the following procedure: 1. Create a LockSet for SYSCON. 2. Use your text editor to create a batch file called TEST.BAT. This batch file should contain the three lines from the previous section. 3. At the DOS prompt, type TEST <ENTER>. The first command in the batch file will now be executed. Once you have secured a position in the LockSet, the following message appears: Position has been obtained in LockSet SYSCON. At this point, the screen for SYSCON displays. You have now successfully gained access to SYSCON. 4. Exit the application. The command "SUNLOCK SYSCON" is executed as soon as you exit SYSCON. The following message appears: Your position has been released in LockSet SYSCON. The following batch file shows examples of using errorlevels in conjunction with SLOCK and SUNLOCK. Here, if the errorlevel returns a successful code, the software package Multimate will be accessed. If not successful, a message will appear on the screen telling the user that all the positions in the LockSet for Multimate are taken. At the end of each course, SUNLOCK will be executed, releasing the position in the LockSet. echo off SLOCK MULTIMATE if errorlevel= 100 goto go goto Again :go MMS.EXE (Multimate) goto end :Again echo 'Try later, Multimate is licensed out...' pause :end SUNLOCK MULTIMATE (metered application name) 1.4.2 Command Line Reference This section displays the correct syntax for SLOCK and SUNLOCK and explains the command line options. The correct syntax for SLOCK is: SLOCK LockSet [*] [S=fileserver] NOTE: The brackets indicate optional entries. Do NOT type the brackets when using these options. OPTION DESCRIPTION LOCKSET This is a required entry. The name of the LockSet must be entered. The LockSet is the metered application. * Displays message flag. Designating this option provides the user with visual confirmation that the commands have been executed. S=fileserver This option denotes the name of the fileserver that contains the LockSet. The correct syntax for SUNLOCK is: SUNLOCK LockSet [*] [S=fileserver] NOTE: The brackets indicate optional entries. Do NOT type the brackets when using these options. OPTION DESCRIPTION LOCKSET This is a required entry. The name of the LockSet must be entered. The LockSet is the metered application. * Displays message flag. Designating this option provides the user with visual confirmation that the commands have been executed. S=fileserver This option denotes the name of the fileserver that contains the LockSet. 1.4.3 Error Levels SiteMeter has two types of error reporting that can be printed to the screen: text messages and numeric codes. Not all programs contain both types of errors. This section explains the numeric codes. All programs will report with an on-screen message when there is an attempt to: o Execute the utility while not using Advanced NetWare o Use any of the utilities while not logged into the network (other than SWATCHER) Numeric code returns are offered for both SLOCK and SUNLOCK. The following sections list these codes. 1.4.4 SLOCK Errorlevels 100 User has successfully obtained a position in the desired LockSet. 99 Bad LockSet name or lock set name is too long. 88 Invalid LockSet name or name does not exist. 77 LockSet is in use by someone using SiteMeter to change some parameter about that set. 66 After testing the LockSet 30 times, it is still locked (not by the Supervisor--77) 58 No slots available in LockSet, you have been queued. 56 No queue slots available (maximum of 8); you were not queued. 55 No slots available in LockSet...try later. 50 Not attached to specified server. 1.4.5 SUNLOCK Errorlevels 100 User's slot has been successfully found and released. 99 Bad LockSet name or LockSet name is too long. 88 Invalid LockSet name; name does not exist. 77 LockSet is in user by someone using SiteMeter to change a parameter about that LockSet. 66 After testing the LockSet 30 times, it is still locked (not by Supervisor--error 77). 55 No slot in use. 50 Not attached to specified server. 33 No rights to SYS:SYSTEM\SITEMETR, or it does not exist. The name (directory) is defined by the SiteMeter Administrator. 22 No network drives are mapped. SUNLOCK 'borrows' one of the current station's network drive letters to update the activity log, but if none exist the activity log will not be updated. 2.0 Appendix B Troubleshooting Appendix A provided information about SiteMeter's advanced utilities. This appendix provides a listing of SiteMeter's error messages and their explanations as well as common troubleshooting tips. 2.1 Error Messages The following error messages may display while using SiteMeter. A print destination must be chosen. Please select a printer in the printer setup dialog box to run a report. A report type must be selected. Please specify a report type in the reports dialog box to run a report. A server must be selected. Please specify a server in the reports dialog box to run a report. A source file must be indicated. Please specify an input source in the reports dialog box to run a report. A valid date range must be provided. Please specify a date range for filter criteria in the reports dialog box to run a report. Are you sure you want to export the data? Choose the Yes button to continue with the export of the data file. At least one filter criteria choice must be given! Please specify at least one of the filter criteria, either date, user, or application. File size exceeds 65,535 lines. Unable to export. The data file is too big to be exported any of the standard formats. Please try Btrieve as the export type. Invalid user name supplied. Please specify a valid user name in the attach dialog box. No additional servers can be found. SiteMeter capability could not detect additional servers. No default printer! Select a printer from PRINT SETUP menu. Please select a printer in the printer setup dialog box to run a report. No input file specified. Cannot continue. Please specify the name of the input file. No output file specified. Cannot continue. Please specify the name of the output file on the export dialog box for data output. No output type specified. Cannot continue. Please select one of the output formats specified in the drop down list. No server specified. Cannot continue. Please select a server to generate reports. No source type specified. Cannot continue. Please specify one of the four radio buttons on the export dialog box for input source. Please select or enter a server name before pressing the OK pushbutton. Please specify a server in the attach or detach dialog box. Report setup choices incomplete. All selections necessary to run reports have not been made in the reports dialog box. The 'sitedata' file has been corrupted. Please contact McAfee Technical Support for assistance. Cannot read the SITEDATA file. Please contact McAfee Technical Support for assistance at 908-530-9650. Unable to establish connection with DataLIB DLL. Cannot continue. Please check to see that the file DLWBC31.DLL is in the same directory as SREPORT.EXE. Unable to initialize Btrieve DLL file. Please check and make sure that the files WBTRCALL.DLL and WBHANDLE.DLL are in the same directory as SREPORT.EXE. Unable to initialize DataLIB DLL; export functions will be unreliable. Please check to see that the file DLWBC31.DLL is in same directory as SREPORT.EXE. Unable to open input file. Cannot continue. Please check to see that the input files SITEDATA or VIRUSDTA are in the directory you have selected. Unable to open output file. Cannot continue. Please check to see that the file DLWBC31.DLL is in the same directory as SREPORT.EXE. When 'File' is the print destination, a file type must be selected. Please specify an output file name to print a report to a file. Would you like to export new baseline source files for your report? Choose the Yes button to continue with the export of the data files. You may choose the No button if you have recently exported the data files. This will save some time in the report generation process. Unable to create Btrieve output file. File may be in use. The Btrieve data output file with extension .DAT may already be in use by another user. Ensure that no one else is using the file and try again. If the problem still persists, please use the Btrieve utility provided by NetWare. Type BUTIL -RESET filename.DAT. Unable to create peaks.dat file. The Btrieve data output file PEAKS.DAT may already be in use by another user. Ensure that no one else is using the file and try again. If the problem still persists, please use the Btrieve utility provided by NetWare. Type BUTIL -RESET PEAKS.DAT. Unable to initialize Btrieve requester. Btrieve requester Brequester may not be running. Please exit Windows and run BREQUEST.EXE. Unable to insert Btrieve record. Btrieve was unable to insert one of the records in the export process. The original file may be corrupted, please call McAfee Technical Support. Unable to open peaks.dat file. The Btrieve data output file PEAKS.DAT may already be in use by another user. Ensure that no one else is using the file and try again. If the problem still persists, please use the Btrieve utility provided by NetWare. Type BUTIL -RESET PEAKS.DAT. Unable to open sitedata.dat file. The Btrieve data output file SITEDATA.DAT may already be in use by another user. Ensure that no one else is using the file and try again. If the problem still persists, please use the Btrieve utility provided by NetWare. Type BUTIL -RESET SITEDATA.DAT. 2.2 Troubleshooting This section describes solutions to some of the common difficulties encountered with SiteMeter. 2.2.1 Installation and Set Up Please see the Quick Start Guide in Chapter 3 for instructions on installation and setup. Chapter 2 provides detailed installation instructions and error messages. 2.2.2 Cannot Meter This section provides a checklist of things to do if you are unable to meter software on your network. An example of this problem would be when a user runs an application but SiteMeter does not show the software as active in View Application Usage or in the Usage.exe program. Follow the items on this checklist: 1. Check if the NLMs are loaded and active. Go into Administration, Metering, View Metering Status. 2. Try placing a full path into the filename field when defining the metered application. If that does not work, try without a path and just a filename. 3. Check if the NetWare drivers are up to date (at a minimum they should be IPX v. 3.10, NETX v. 3.26, IPXODI v. 2.10, LSL v. 2.01). 4. If the user is loading SWATCHER, make sure it is loaded low. Swatcher is only designed to be loaded into conventional memory (640K). 5. Check for additional, interfering TSRs or drivers. Do a MEM /C | MORE to see what is loaded in memory and strip the PC of all TSR's and drivers besides the NetWare drivers and whatever is absolutely necessary for Windows. To do this, rename the autoexec.bat file to autoexec.old and remove from the config.sys file all unnecessary drivers. For instance, WordPerfect Office v. 3.1's Notify TSR may prevent a DOS application from releasing the lockset. 6. Check the win.ini file's load= statement. Test with only NWPOPUP on the load= statement. 7. SPAWNING. Check if the file that is being metered is SPAWNING. A file that spawns opens up one file, closes it and then opens up a different file. For example, WordPerfect For Windows v. 5.1 first opens WPWIN.EXE. It then closes WPWIN.EXE and opens or spawns to WPWINFIL.EXE. This means that WPWINFIL.EXE is the file to meter for WordPerfect For Windows. To check for what file to meter, run RCONSOLE or walk over to the fileserver console. Run Monitor. Then List Active Connections and select Connection Information. Select the name of the user. Then have the user run the application. The files that remain open in Monitor for that user's PC will be displayed and you will be able to identify the files running for the application. As of this writing, SiteMeter v. 4.1.1 or earlier requires that an .exe or .com file must be open in order to meter an application. The secondary file or files that are spawned may not have an .exe or .com extension and this sometimes results in the application not metering or the lockset not being released when the application is closed. If this is the case and the application is a DOS based program, SLOCK and SUNLOCK may be used to meter the program. SLOCK and SUNLOCK are metering utilities which shipped with SiteLock. Simply create a batch file which runs SLOCK, the DOS application and then SUNLOCK. For example, let's say the program is SYSCON. The .bat file that would be set up could be called SYSCON.BAT. The contents of the .bat file would be, SLOCK SYSCON_UTIL SYSCON.EXE SUNLOCK SYSCON_UTIL where SYSCON_UTIL is the Metered Application Name in the Currently Metered Application under Metering. When the user types SYSCON, SYSCON.BAT will execute and SLOCK will run, manually placing a lock on the metered application. Then SYSCON.EXE will run. When the user exits SYSCON, SUNLOCK will run, manually releasing the lock in SiteMeter. NOTE: Spawning will be addressed by an enhancement in a future release of SiteMeter/BrightWorks. Please see the appropriate sections in Appendix A for further information on Slock and Sunlock. Another workaround is to list all of the .exe or .com files under File[s] To Meter in the metered application. This sometimes gets the application to meter properly and/or release the lockset. Especially try this with Windows based applications because there is no workaround like Sunlock to catch a spawned Windows based application. An additional workaround is to modify the SITEMETR.EXT file. The Sitemetr.ext file exists in the Home Directory For Data Files (SYS:SYSTEM\SITEMETR). It contains a listing of the extensions of the files that can be accepted as the File[s] To Meter in a metered application. By editing this file, the Supervisor (or equivalent) will then be able to enter a filename with the new file extension as a File[s] To Meter. It may then be possible to meter an application without a .exe or .com extension. In our experience, the only applications that were able to be metered this way were Micrographic programs. These programs include Designer, Draw and Charisma. These programs spawn to a .BIN file which SiteMeter cannot normally meter. The workaround for the SITEMETR.NLMs is as follows: a. Edit the SYS:\SYSTEM\SITEMETR\SITEMETR.EXT file and add .BIN to the list of file extensions. b. Enter (DESIGNER).BIN as the File[s] To Meter in the Currently Metered Application under SiteMeter (SYS:\DESIGNER\DESIGNER.BIN). NOTE: For SWATCHER, the workaround to meter Micrographics programs is quite different: Delete the original Designer.exe file and rename the Designer.bin file to Designer.exe. Copy that new .EXE file into the <MGXLIBS> subdirectory. Within File[s] To Meter include the specific path and correct .EXE file to protect. Other programs such as Draw and Charisma can do the same. Rename or delete the .EXE file and copy the .BIN file to a .EXE file. 8. Remove items from the Windows Startup group and test. 9. Reload the Sitemetr and Smrproxy NLMs. 10. If the SiteMeter NLMs are being loaded after Macintosh NLMs (AFP.NLM, ATPS.NLM), load the SiteMeter NLMs before the Macintosh NLMs. In the past, having the SiteMeter NLMs loaded after Macintosh NLMs sometimes caused the fileserver to crash and/or metering to fail. 11. Check if the old SiteLock NLM is simultaneously loaded with Sitemetr.nlm and Smrproxy.nlm. This could have disastrous, random results. If so, remove Sitelock.nlm. 12. Recreate the lockset. Go Metering, Currently Metered Applications and delete the entry for the software package that will not meter. Then add the entry back into the metering database and retest. 2.2.3 LockSet Does Not Release For example, a user enters Lotus 1-2-3. After exiting the program, View Application Usage or USAGE.EXE still shows the user in the application when they are not in the application. To troubleshoot this situation, usually the affected PC must first release the lockset. To do this, have the user with the locked application either back out of Windows or log out of the network. Follow this checklist to solve this problem: 1. Do one of the following: a.Place the full path into the File[s] To Meter field. For example, SYS:\PUBLIC\SYSCON.EXE. Go into Metering and Modify the currently metered application. 'Remove' the file that is already present and then 'Add' to Browse For Files To Meter. Make sure the Include Path box is marked. Then browse for the filename and it will appear in the File[s] To Meter window with the full path. b. If the path already exists in the File[s] To Meter field, remove the path and just leave the filename using similar steps as in 1a. For example, 123.EXE. Make sure the Include Path box is blank. 2. If the user has loaded the SWATCHER TSR, make sure that Swatcher is NOT loaded high. Swatcher was designed to only be loaded in conventional memory (640 K). 3. Check if the NLMs are loaded and active. Go Administration, Metering, View Metering Status. 4. Ensure that the user has loaded the latest NetWare drivers (IPX, IPXODI, LSL and NETX). 5. SPAWNING. Check if the application spawns other files. As of this writing, SiteMeter v. 4.1.1 or earlier requires an open .exe or .com file to meter an application. This will be addressed by an enhancement in a future release. The secondary file or files that are spawned may not have an .exe or .com extension and this sometimes results in the lockset not being released when the application is metered. If this is the case and the application is a DOS based program, SUNLOCK may be used to release the lockset. SUNLOCK is a metering utility which shipped with SiteLock. Simply create a batch file which runs the DOS application and then runs SUNLOCK. For example, lets say the program is SYSCON. The .bat file that would be set up could be called SYSCON.BAT. The contents of the .bat file would be, SYSCON.EXE SUNLOCK SYSCON_UTIL where SYSCON_UTIL is the Metered Application Name in the Currently Metered Application under Metering. When the user types SYSCON, SYCON.BAT will execute and SYSCON.EXE will run. When the user exits SYSCON, SUNLOCK will run, manually releasing the lockset in SiteMeter. Please see Appendix A for further information. Another workaround is to list all of the .exe or .com files under File[s] To Meter in the metered application. This sometimes gets the application to meter properly and release the lockset. Especially try this with Windows based applications, because there is no workaround like Sunlock to catch a spawned Windows based application. 6. Check for additional, interfering TSRs or drivers. Do a MEM /C | MORE to see what has been loaded into memory and strip the PC of all TSR's and drivers besides the NetWare drivers and whatever is absolutely necessary for Windows. To do this, rename the autoexec.bat file to autoexec.old and remove from the config.sys file all unnecessary drivers. For instance, WordPerfect Office v. 3.1's Notify TSR may prevent a DOS application from releasing the lockset. 7. Remove items from the Windows Startup group and test. 8. Check the PC's win.ini file's load= statement. Test with only NWPOPUP on the load= statement. 9. Check if the old SiteLock NLM is simultaneously loaded with Sitemetr.nlm and Smrproxy.nlm. This could have disastrous results. If the Sitelock.nlm is loaded, REMOVE the Sitelock.nlm from the fileserver's memory and the autoexec.ncf file. 10. Recreate the lockset. Go Metering, Currently Metered Applications and delete the entry for the software package that will not meter. Then add the entry back into the metering database and retest. 11. QEMM v. 7.01. Can't release a lockset for an application that is called off an attached server due to QEMM v. 7.01. The workaround is to remove the LOADHI command from the SHELL= line in the workstation's CONFIG.SYS. QEMM's v7.xx of Optimize places this LOADHI command on the SHELL= line. Apparently, previous versions of Optimize did not do this. 12. DR DOS v. 6.0. It is suspected that you can't release a lockset on a PC running DR DOS v. 6.0. Use a different type of DOS. NOTE: This problem also applied to DOS applications run under Windows. 13. NET-PROT. It is possible that with the NETPROT.NLM v. 1.23 loaded, intermittently locksets do not release or SiteMeter fails to meter. Results from in-house testing revealed that locksets on DOS applications are not released. This only seems to occur if an active virus scan is being performed by Net-Prot. Locksets on Windows applications seem to meter fine but will occasionally not be released. This does not seem to follow any pattern. However, if an active virus scan is being performed by Net-Prot, SiteMeter will NOT release locksets. This issue is currently under investigation. 2.2.4 SMRUP Patches The following sections describe the various patches available for SiteMeter. 2.2.5 SMRNLM.EXE 73,092 6-02-94 SMRNLM.EXE only contains the current SiteMeter NLMs, current SMRAGENT.EXE file and the current SITEMETR.MSG file (along with a read me file SMRNLM.DOC). SMRNLM.EXE supports versions of SiteMeter v. 4.00 or greater. The updated version of SMRAGENT.EXE included here addresses an "out of memory" message that could display in Windows (Occurred with SMRAGENT 3-09-94). If a user needs only the current NLMs or SMRAGENT, SMRNLM.EXE is the file to use. o 351108 05-04-94 12:12 SITEMETR.NLM o 21168 04-01-94 13:26 SMRAGENT.EXE o 74972 05-04-94 12:18 SMRPROXY.NLM o 1439 02-10-94 10:29 SITEMETR.MSG o 3557 06-02-94 SMRNLM.DOC Other items SMRNLM.EXE addresses: 1. Sometimes cannot meter or virus protect applications run from a map rooted drive. 2. SMRPROXY NLM cannot be loaded without first disabling NetWare Accounting. 3. The fileserver would sometimes abend upon a DOWN command. 4. Sometimes a SPX socket problem occurred with SMRAGENT 8-17-93. This sometimes occurred with other programs that open SPX sockets inside Windows such as a mail TSR or Windows For Workgroups. Symptoms include, "SiteMeter agent Error 7: There was an IPX Problem communicating with server" or "Wcnwlib error: Unexpected error opening socket" or PC lock ups. This problem also results in "Error 001: cannot communicate with VAP or NLM" with the SiteLock Swrap feature. 5. IPX Traffic. Sometimes when the 7-20-93 Sitemetr.nlm and the 8-5-93 Smrproxy.nlm were loaded, fileserver utilization might increase and possibly no one could login. 6. Locksets were not released with SMRAGENT 2-14-94, byte count 29,776. 7. When INSTALL is loaded at the fileserver, the fileserver would sometimes abend (occurred with SITEMETR.NLM 2-13-94 and SMRPROXY.NLM 2-14-94). 2.2.6 SMRUP3.EXE 05-25-94 1,788,902 11:48a On 5-25-94 the SMRUP2.EXE patch was released. IT IS ONLY APPLICABLE TO SITEMETER v. 4.10 USERS. IT IS NOT APPLICABLE TO SITEMETER v. 4.00 USERS. SMRUP3 is a self-extracting file dated 5-25-94 and contains the following files: o READ1ST.TXT 9,714 05-18-94 11:27a o SITEMTR.EXE 1,774,855 05-17-94 5:17p SITEMTR.EXE consists of the following files: o DPRODREG.EXE 77,437 03-18-94 2:10p; used for serialization only o FIELD .DDF 55,296 04-28-94 11:27a o FILE .DDF 7,680 04-28-94 11:27a o SITEMETR.EXE 1,175,568 05-09-94 5:54p o FUSION .CFG 55 11-15-93 7:05p; used for serialization only o INDEX .DDF 11,776 04-28-94 11:27a o NWCALLS .DLL 146,544 11-02-93 2:30p o NWIPXSPX.DLL 38,544 11-02-93 5:47p o NWLOCALE.DLL 38,576 11-02-93 6:12p o NWNET .DLL 205,104 11-02-93 5:12p o NWNETAPI.DLL 106,884 01-07-93 1:31p o SERIAL .BAT 32 03-17-94 4:33p; used for serialization only o SITEMETR.NLM 351,108 05-04-94 12:12p o SMRAGENT.EXE 21,168 04-01-94 1:26p o SMRPROXY.NLM 74,972 05-04-94 12:18p o US_AD .RPT 17,008 03-22-94 4:57p o VENDOR .LIS 1,745 03-31-93 11:36a o UFLBWRKS.DLL 32,640 05-03-94 05:03p o CHISHWSV.RPT 25,951 05-04-94 02:51p o CHISHWMC.RPT 23,809 05-04-94 03:03p o CHISHWPC.RPT 25,423 05-04-94 11:05a o UPF .RPT 9,562 03-22-94 04:39a o US .RPT 14,949 03-22-94 04:44p o US_AS .RPT 15,853 03-24-94 04:05p o SPA .RPT 7,942 03-22-94 04:35p o SWINAPP .EXE 49,680 05-04-94 12:06p o SREPORT .EXE 116,752 05-09-94 05:30p o SYSMOD .EXE 44,192 05-04-94 12:08p o USAGE .EXE 130,064 05-04-94 01:44p o SDUPDATE.EXE 136,736 05-04-94 11:55p o SA_EQUIP.EXE 272,421 05-02-94 04:35p o WSDUPD .EXE 21,504 05-04-94 12:03p o EQUIP .EXE 174,607 05-02-94 04:17p o CRW .EXE 1,768,448 05-04-94 04:56p o QUICKST .WRI 17,536 05-09-94 10:37a; a guide to getting started o DELID .EXE 16,318 05-04-94 11:35a o SPF .RPT 9,622 03-22-94 04:38p o AS_UD .RPT 18,218 03-22-94 03:36p o AS .RPT 14,318 03-22-94 03:38p o AS_US .RPT 16,592 03-22-94 04:13p o WSREPOT .RPT 26,961 04-22-94 04:51p o METERDEF.RPT 7,416 03-23-94 05:03p o BDIABOUT.DLL 424,464 05-11-94 12:34p o SMRXPORT.DLL 67,628 04-17-94 04:46p o README .TXT 36,144 05-13-94 01:37p; updated with the new changes o SMR .BAT 158 05-17-94 02:26p; to remove old files SITEMETR.EXE contains updated NLMs, DLLs, and EXEs for BrightWorks v1.0.1, LAN Automatic Inventory 3.1.1 and SiteMeter v4.1.1. (Please note that the NLMs and SMRAGENT.EXE included here are the same versions of those files that are contained within FUSUP3.EXE of PCVEND LIB3). The updated version of SMRAGENT.EXE included here addresses an "out of memory" message that could display in Windows (Occurred with SMRAGENT 3-09-94). Also included in SITEMTR.EXE are updated Data Dictionaries (DDFs). These DDFs now combine Inventory and Metering data structures into the same group of definition files. In addition, an update to the canned Metering report "Application Use with User Detail" (US_AD.RPT) addresses an issue wherein the Date could appear in the Time Out field. It also includes an updated message file for the SiteMeter NLMs. The following list details what other fixes are included in this patch. These errors sometimes occurred with SiteMeter v. 4.0 and the patches released up to, but not including, SiteMeter v. 4.1: 1. Sometimes cannot meter or virus protect applications run from a map rooted drive. 2. SMRPROXY NLM cannot be loaded without first disabling NetWare Accounting. 3. The fileserver would sometimes abend upon a DOWN command. 4. Sometimes a SPX socket problem occurred with SMRAGENT 8-17-93. This sometimes occurred with other programs that open SPX sockets inside Windows such as a mail TSR or Windows For Workgroups. Symptoms include, "SiteMeter agent Error 7: There was an IPX Problem communicating with server" or "Wcnwlib error: Unexpected error opening socket" or PC lock ups. This problem also results in "Error 001: cannot communicate with VAP or NLM" with the SiteLock Swrap feature. 5. IPX Traffic. Sometimes when the 7-20-93 Sitemetr.nlm and the 8-5-93 Smrproxy.nlm were loaded, fileserver utilization might increase and possibly no one could login. 6. Locksets were not released with SMRAGENT 2-14-94, byte count 29,776. 7. When INSTALL is loaded at the fileserver, the fileserver would sometimes abend (occurred with SITEMETR.NLM 2-13-94 and SMRPROXY.NLM 2-14-94). SiteMeter v. 4.1.1 contains these updated files: o SMRPROXY.NLM 74,972 5-04-94 o SITEMETR.NLM 351,108 5-04-94 o SMRAGENT.EXE 21,168 4-01-94 o SITEMETR.MSG 1,439 2-10-94 2.2.7 SiteMeter Reports (Sreport.exe) As of this writing, SREPORT.EXE 5-9-94, 116,752 bytes is the current SiteMeter Report file. It ships with SiteMeter v. 4.1.1. It is available in a patch file SMRRPT3.EXE which is on Compuserve, GO BRIGHT, LIB 3. 1. "Sreport caused a GPF in module DLWBC31.DLL". A General Protection Fault error occurs when a user Exports a 65K or greater Sitedata file to non-btrieve format (i.e., Excel, etc.). This is an open issue currently under investigation. To workaround the issue, rename the Sitedata file before it reaches 65K in size. 2. Btrieve error code 20, cannot run Sreport". This means that SREPORT.EXE detected that Btrieve was not loaded properly. o Local Btrieve or brequest.exe are INDEED not loaded. o SPX is not loaded (when using brequest and server btrieve. IPXODI has the option of disabling SPX. Enable SPX). Make sure IPXODI is NOT loaded with a /d or /a switch. /d prevents IPXODI from loading SPX. o BSPXCOM.NLM is not loaded. o Ensure that VIPX.386 is version 1.17 or later if IPXODI is being loaded high. If VIPX.386 is version 1.1 and IPXODI is loaded high, the SPX could fail and cause the BTRIEVE error 20. o Make sure the NOVDB.INI file exists in the \Windows directory. o If the user is attached to multiple fileservers, have them log into just the one server where SiteMeter/BrightWorks is installed. 3. Sreport caused a GPF in module CRPE.DLL @ 0026:0A03". Resolved by SREPORT 5-9-94, byte count 116,752. Get SMRUP3.EXE file from Compuserve. 4. No information shows in a SiteMeter report done for a date range of one day. For a workaround, do a report with a date range greater than one day. This is an open issue that is currently being investigated. 5. Peaks calculation problem. Resolved by SREPORT 5-9-94, byte count 116,752. Get SMRUP3.EXE file from Compuserve. 6. "Unanticipated Btrieve Error #1". User gets this error if they use Brequest v. 6.10d. This error also occurs with BREQUEST.EXE v6.10e. Use Brequest v. 6.10c, or later, instead. Btrieve v. 6.10c is available on Compuserve. GO NOVLIB, Library 7 and download the file BTR61.EXE. 7. Negative number problem. User gets negative numbers in the report data. First addressed by SREPORT 3-24-94. Get SMRUP3.EXE file from Compuserve. 8. An update to the "canned" report file US_AD.RPT resolved an issue wherein the Date could appear in the "Time Out" field of the "Application Use with User Detail" report. First addressed on 3-15-94. Get SMRUP3.EXE file from Compuserve. 9. The "Defined Limit" field of the Metering Definitions could reflect an incorrect value. First resolved with 3-24-94 Sreport. Get SMRUP3.EXE file from Compuserve. 10. A GPF that could be caused by UFLSAMP1.DLL. First resolved with Sreport 3-24-94. Get SMRUP3.EXE file from Compuserve. 11. The SMRPT2.EXE file included updated .dll files so as to be in sync with the same files that existed in the Fusion v1.00 package and in FUSUP2.EXE patch file on Compuserve, LIB3, PCVEND. SMRUP3.EXE patch contains these files as well. 12. GPF caused by UNIDRV.DLL. SiteMeter reports would give a GPF in UNIDRV.DLL when the Printer Icon was used to print from an open report window and the user then exited and re-entered the SiteMeter reports. This is an OPEN issue. The workaround is to either close all of the open report windows before exiting SiteMeter Reports or to have the user downgrade to an earlier version of UNIDRV.DLL. 13. Corrupt Sitedata file? When the SiteMeter Reports fail, another possibility is that the SITEDATA file has become corrupt (or SITEDATA does not exist because no one has been metered yet and caused SITEDATA to be created by the NLMs). A quick method of verifying this is to divide the byte size of the Sitedata file by 49. If the result is not a round number, the file is corrupt. The Sitedata Debugger program may be used to fix the file. To have the Debugger come up in SREPORT, create a SREPORT.INI file in the \WINDOWS directory. It should contain, [Debug] Enabled=1 file type=10 An alternative is to send the Sitedata file to McAfee East Tech Support by Compuserve or the mail so we can fix it with the Sitedata Debugger program. 2.2.8 BTRIEVE This section contains common SiteMeter Btrieve errors and solutions. 1. "Btrieve record manager inactive". Have the user type PATH. This will show all of their search drives. Then have the user do a dir on WBTRCALL.DLL in each of the search drives. If they come across another copy of WBTRCALL.DLL it means the user may be loading the wrong WBTRCALL.DLL file for Btrieve. 2. User runs the SiteMeter reports and gets "Unable to allocate memory for Btrieve". This error is caused by not having enough free conventional memory. a. Load BREQUEST in the WINSTART.BAT file so it does not load in conventional memory. b. Free up some conventional memory and restart (i.e. remove TSRs, etc.). It has been reported that about 508K of free memory is needed to run the SiteMeter Reports. 3. User runs the SiteMeter Reports and gets "Page Size Error - Btrieve error 24". a. The user must run BREQUEST or BTRIEVE at the workstation. b. Free up memory. Load items high (LSL, NIC driver, etc.) and/or load BREQUEST into high memory by loading it in the WINSTART.BAT file. 2.2.9 Changing the SiteMeter Messages A user may request to change the text of a message in SiteMeter. The method to do this is to go into the SYS:SYSTEM\SITEMETR directory (or wherever the Home Directory For Data Files are located. Go Administration, Metering, Configuration Options). Then have the user make a backup of the SITEMETR.MSG file. They can then use a text editor to change the messages. Then the user must reload the SiteMeter NLMs.